The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Install application programming interfaces (APIs) suitable to the game’s data source provider
|
|
Research appropriate APIs Completed |
Evidence:
|
Identify specific APIs as suitable for the game architecture and data source provider Completed |
Evidence:
|
Install nominated APIs on game development computers Completed |
Evidence:
|
Define and use a connection to the data source
|
|
Define game data source connection parameters Completed |
Evidence:
|
Store connection parameters in external text-based configuration file Completed |
Evidence:
|
Open and close connection to the game data source Completed |
Evidence:
|
Configure and use connection pooling
|
|
Configure connection pooling in the database management system Completed |
Evidence:
|
Define connection pool parameters for minimum connections, maximum connections and idle connections Completed |
Evidence:
|
Minimise use of database resources through the use of connection pooling Completed |
Evidence:
|
Test and verify use of connection pooling Completed |
Evidence:
|
Pass embedded structured query language (SQL) to the database
|
|
Define database connection property Completed |
Evidence:
|
Compose SQL statement or command to be passed to the database Completed |
Evidence:
|
Test, debug and execute the SQL statement Completed |
Evidence:
|
Execute a stored procedure on a database
|
|
Call a stored procedure on the database using command callable statement Completed |
Evidence:
|
Define and pass parameters to the stored procedure Completed |
Evidence:
|
Test, debug and execute database stored procedure Completed |
Evidence:
|
Modify database data
|
|
Retrieve multi-row multi-column result sets from the database into the game application domain Completed |
Evidence:
|
Insert new records into the database Completed |
Evidence:
|
Update existing database records Completed |
Evidence:
|
Delete existing database records Completed |
Evidence:
|
Integrate data from the database with the game application domain
|
|
Integrate data from a forward-only and read-only cursor into the game application domain Completed |
Evidence:
|
Incorporate data from an updateable cursor into the game application domain Completed |
Evidence:
|
Test and debug database integration code
|
|
Test database integration code Completed |
Evidence:
|
Document test results Completed |
Evidence:
|
Determine errors and exceptions and document solutions Completed |
Evidence:
|
Debug all errors and exceptions Completed |
Evidence:
|
Assess all data modifications in the database and document any errors Completed |
Evidence:
|
Correct all causes to data modification errors Completed |
Evidence:
|